Risk Signal: Brazilian CPF Number Check
The Jumio CPF check allows customers to validate the CPF Number. CPF is the Brazilian Individual Taxpayer Registry Identification number, referred to as Cadastro de Pessoas Fisicas (Portuguese for “Natural Persons Register”). A CPF number is a permanent number printed on current driver’s licenses (DL) & ID versions. A CPF number is assigned to both Brazilians and resident aliens who are subject to taxes in Brazil.
The CPF Number Validation service will send the extracted CPF number from the DL & ID to the Tax ID database in order to:
-
Retrieve the status of the CPF number.
-
Compare the name returned from the database with the name provided for the transaction.
-
Map the results and return the status of the match.
Supported Credentials
The following values can be uploaded as Prepared Data. Alternatively, they can be extracted by an upstream capability in a workflow.
To use Prepared Data with the CPF Number Check as a standalone capability use workflow key 10005.
Key |
Type |
Mandatory |
Description |
---|---|---|---|
id.idNumber |
string |
yes |
for Brazil, this will be CPF number |
id.type |
string |
no |
ID_CARD or DL |
firstName |
string |
Must include firstName or lastName, and may include both.* |
first name |
lastName |
string |
Must include firstName or lastName, and may include both.* |
last name |
dateOfBirth | string | no | YYYY-MM-DD. Will influence risk score if provided. |
address.country |
string |
yes |
country should be ISO Alpha 3 Code only |
* The concatenated values of the firstName and lastName fields are matched against the name on record for the CPF number.
Example Prepared Data Body
{ "firstName": "pris****", "lastName": "da *****", "dateOfBirth":"1982-MM-08", "address": { "country": "BRA" }, "id":{ "idNumber":"28908936***", "type":"ID_CARD" } }
Response
Response data is available for transactions that include the risk signal. For information on transaction data see Viewing or Retrieving Workflow Transactions.
Example Response
"braCpfValidation": [ { "id": "efbb1f08-****-43d3-b4e6-******30bb76", "credentials": [ { "id": "20d0613b-11d6-4d25-97e9-60fffad*****", "category": "DATA" } ], "decision": { "type": "PASSED", "details": { "label": "OK" } }, "data": { "nameMatch": "MATCH", "cpfMatch": "MATCH", "dateOfBirthMatch": "MATCH" } }]
Decision Details Labels
Decision Type |
Label |
Description |
---|---|---|
PASSED |
OK |
The provided data matched |
REJECTED |
DENY |
The provided data did not match what was on record. |
WARNING |
ALERT | The CPF number is valid but either the name or DOB do not exactly match. |
NOT_EXECUTED |
NOT_ENOUGH_DATA |
The provided data was inadequate to process the transaction. |
NOT_EXECUTED | TECHNICAL_ERROR |
Data
Key |
Possible Values |
Description |
---|---|---|
nameMatch |
MATCH NOT_MATCH |
To be a MATCH the concatenated firstName and lastName value of the input data must exactly match what is in the CPF database. |
cpfMatch |
MATCH NOT_MATCH |
CPF number matches. |
dateOfBirthMatch |
MATCH NOT_MATCH |
Date of birth matches. |